System and method for sharing data based on a combined bandwidth consumption

ABSTRACT

A system, method, and computer program product are provided for sharing data based on a combined bandwidth consumption. In use, a first sharing action is received. Next, a first bandwidth consumption is received. Further, a second bandwidth consumption is received. Additionally, it is determined whether a combination of the first bandwidth consumption and the second bandwidth consumption surpasses a predefined threshold. Lastly, the first sharing action is conditionally allowed based on the determination. Additional systems, methods, and computer program products are also presented.

FIELD OF THE INVENTION

The present invention relates to sharing data, and more particularly tosharing data based on a combined bandwidth consumption.

BACKGROUND

Traditional mobile computing systems are limited by one or more datatransmission limits associated with total bandwidth consumption. Forexample, a user's mobile account may be associated with an allocatedbandwidth consumption amount. Further, bandwidth consumption amounts maynow be shared amongst more than one device. However, use of theallocated bandwidth amongst more than one device can potentially beexceeded and be inaccurately tracked at each device. As such, there isthus a need for addressing these and/or other issues associated with theprior art.

SUMMARY

A system, method, and computer program product are provided for sharingdata based on a combined bandwidth consumption. In use, a first sharingaction is received. Next, a first bandwidth consumption is received.Further, a second bandwidth consumption is received. Additionally, it isdetermined whether a combination of the first bandwidth consumption andthe second bandwidth consumption surpasses a predefined threshold.Lastly, the first sharing action is conditionally allowed based on thedetermination. Additional systems, methods, and computer programproducts are also presented.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a method for sharing data based on a combined bandwidthconsumption, in accordance with one embodiment.

FIG. 2 shows a system for sharing data based on a combined bandwidthconsumption, in accordance with one embodiment.

FIG. 3A illustrates a digital photographic system, in accordance with anembodiment.

FIG. 3B illustrates a processor complex within the digital photographicsystem, according to one embodiment.

FIG. 3C illustrates a digital camera, in accordance with an embodiment.

FIG. 3D illustrates a wireless mobile device, in accordance with anotherembodiment.

FIG. 3E illustrates a camera module configured to sample an image,according to one embodiment.

FIG. 3F illustrates a camera module configured to sample an image,according to another embodiment.

FIG. 3G illustrates a camera module in communication with an applicationprocessor, in accordance with an embodiment.

FIG. 4 illustrates a network service system, in accordance with anotherembodiment.

FIG. 5 illustrates a method for determining whether to perform anaction, in accordance with another embodiment.

FIG. 6 illustrates a message sequence for determining bandwidthconsumption, in accordance with another embodiment.

FIG. 7 illustrates a method for reducing data associated with an action,in accordance with another embodiment.

DETAILED DESCRIPTION

FIG. 1 shows a method 100 for sharing data based on a combined bandwidthconsumption, in accordance with one embodiment. As an option, the method100 may be implemented in the context of the details of any of theFigures. Of course, however, the method 100 may be carried out in anydesired environment. Further, the aforementioned definitions may equallyapply to the description below.

As shown, a first sharing action is received. See operation 102. Next, afirst user indication of a first bandwidth consumption is received. Seeoperation 104. Further, a second user indication of a second bandwidthconsumption is received. See operation 106.

In the context of the present description, a sharing action includes anyaction to share data in some manner. For example, in variousembodiments, sharing action may include an action to transfer data fromone client to another client, from a client to a server, from a serverto a client, within a network, from a network to a second network, tothe cloud, etc.

Additionally, in the context of the present description, bandwidthconsumption is an amount of data conveyed through one or more networks(in other words, “used” or “consumed”). For example, in one embodiment,a user may have a wireless data connection provided as part of a dataservice plan associated with a mobile network carrier, and the user maytransmit and/or receive data through the mobile network carrier, therebyconsuming bandwidth against a data allocation specified in the dataservice plan. Bandwidth may be consumed by one or more sharing actions.In one embodiment, the first bandwidth consumption may comprise anamount of bandwidth consumed against a data allocation associated with awireless data service (e.g. bandwidth consumed through a mobile networkcarrier), while the second bandwidth consumption may comprise an amountof data associated with performing an action, such the one or moresharing actions.

In one embodiment, the indication of the first bandwidth consumption maybe received from a network carrier. For example, in one embodiment, theamount of data a user has used may be indicated by the mobile carrier.The second bandwidth consumption may be received by an application orsharing module executing within a client (e.g. a mobile device) thatdetermines total data transmission requirements for a sharing action. Inanother embodiment, the first bandwidth consumption may be received froma peer-to-peer network usage tracking system or usage counter. Forexample, in one embodiment, each device among a collection of devices(e.g. on a shared data plan, etc.) may track individual data consumptionfor the device, and subsequently update other devices within thecollection of devices with the individual data consumption information.With each device receiving individual data consumption information fromall other devices within the collection of devices (e.g. on a shareddata plan, etc.), collective consumption may be known to each device. Avalue for collective consumption may be determined by adding deviceconsumption associated with individual data consumption information. Inone embodiment, the value for collective consumption indicates a totalamount of bandwidth consumed over all devices within a shared data plan.

In another embodiment, one or more usage parameters comprising the firstbandwidth consumption may be received from a peer-to-peer network, andthe peer-to-peer network may periodically receive updates from a networkcarrier regarding the first bandwidth consumption. For example, in oneembodiment, each client in a collection of devices (e.g., on a shareddata plan, etc.) may track device usage and share the device usageinformation with other devices within the collection of devices. In thisway, each device within the collection of devices has complete deviceusage information for the whole collection of devices, and thereforetotal plan consumption. In one usage scenario, each device registered toa shared data plan is able to report total plan usage to a correspondinguser by combining device usage values for devices registered to theshared data plan. Additionally, in certain embodiments, the total amountof bandwidth consumed (as locally reported and saved on each device) maybe cross-checked with a network carrier to ensure that the total amountas determined by the devices is within a set range (e.g. within a fewpercentage points of difference, etc.). If the total amount is notwithin a set range, then the total amount (as saved by each of thedevices) may be updated by the network carrier to reflect the latesttotal amount.

In one embodiment, a network carrier may provide the first userindication of the first bandwidth consumption in response to a query ofusage associated with a first user. Additionally, the network carriermay provide the second user indication of the second bandwidthconsumption in response to a query of usage associated with a potentialsharing action. For example, in one embodiment, a network carrier mayverify an account associated with a user to determine how much bandwidthhas been consumed by that user (or collection of users/devices, etc.).

In one embodiment, each device within the collection of devices executesa background process that performs updates to a locally cached value forthe first bandwidth consumption when the device is within a coveredservice area. For example, each device may perform a periodic (e.g.every ten minutes) update to the locally cached value of the firstbandwidth consumption. In other embodiments, each device may query anetwork carrier data management system (e.g. an accounting system) toretrieve the first bandwidth consumption for an associated shared dataplan. Still yet, in one embodiment, the first bandwidth consumption mayreflect actual bandwidth consumption as calculated by a network carrier.Additionally, in another embodiment, the peer-to-peer network mayprovide individual data consumption information from all devices to eachdevice associated with a shared data plan, thereby allowing each deviceto locally calculate the first bandwidth consumption for the shared dataplan.

As shown, it is determined whether a combination of the first bandwidthconsumption and the second bandwidth consumption surpasses a predefinedthreshold. See operation 108. Lastly, the first sharing action isconditionally allowed based on the determination. See operation 110.

In one embodiment, a predefined threshold may be a data limit (e.g.imposed by a network carrier, etc.). For example, the predefinedthreshold may be defined by a data plan total limit, or a limitassociated with a per user portion of a data plan total limit. Inanother embodiment, if the predefined threshold is surpassed, the firstsharing action may be denied or postponed pending user approval. Forexample, in one embodiment, if a user wants to upload a 100 MBcollection of photos, and doing so would surpass a predefined threshold,then the upload would be denied or, alternatively, the user would needto confirm their decision to exceed the predefined threshold andoptionally purchase an additional allocation of data. For example, inone embodiment, the predefined threshold may be reconfigured, including,for example, adding additional money and/or an additional bandwidthamount to a user's account. In such an embodiment, the predefinedthreshold may be adjusted. In one embodiment, the user may purchase anadditional bandwidth amount for their exclusive use. Alternatively, theuser may purchase an additional bandwidth amount to be shared among allusers registered to the same account. Still yet, in one embodiment, theadjustment may include purchasing additional bandwidth associated withthe shared account (or any account). In another embodiment, if thepredefined threshold is not surpassed, the first sharing action may befully allowed.

Further, in another embodiment, specific types of data may be excludedfrom measuring the first bandwidth consumption and the second bandwidthconsumption. For example, in one embodiment, data associated with music,video, photos, and/or a device app may be excluded from data consumptionassociated with a user. In certain embodiments, music, videos, photos,or other content associated with a preferred service may be excludedfrom measuring the first bandwidth, but music, videos, photos, or othercontent from a non-preferred service may be included in measuring thefirst bandwidth. In one embodiment, a network carrier may track alldata, but only specific types of data may be counted with respect to apredefined threshold.

In one embodiment, the conditionally allowing may depend on an effect ofthe first sharing action. Additionally, in one embodiment, the effectmay include a total amount of bandwidth utilized as a result orpotential result of the first sharing action. In a further embodiment,the first bandwidth consumption, the second bandwidth consumption, andthe effect may be summed to determine whether the predefined thresholdis surpassed. Moreover, the predefined threshold may be associated witha predefined limit associated with a first account, such as an accountassociated with a shared data plan.

For example, in one embodiment, an effect of the first sharing actionmay include transferring data which may exceed a predeterminedthreshold. Because the effect would exceed a predetermined threshold,the first sharing action may be denied or postponed pending userapproval.

FIG. 2 shows a system 200 for sharing data based on a combined bandwidthconsumption, in accordance with one embodiment. As an option, the system200 may be implemented in the context of the details of any of theFigures. Of course, however, the system 200 may be carried out in anydesired environment. Further, the aforementioned definitions may equallyapply to the description below.

As shown, system 200 may include device 202, server 204, devices 206,and a network 208. In various embodiments, device 202 and devices 206may include any device capable of transmitting data via a network system(e.g. mobile phone, tablet, desktop computer, etc.). In one embodiment,the device 202 may include a bandwidth consumption 210, and the devices206 may include a bandwidth consumption 214. Further, the server 204 mayinclude a bandwidth consumption 212.

In one embodiment, the server 204 may monitor data usage for all devicesfor an account. The account may include device 202 and any number ofadditional devices, shown as devices 206. As an example, the device 202and at least one other device may be part of a single account plan witha shared data plan. In such an embodiment, the server 204 may track thebandwidth consumed for the device 202 and the at least one other device.Such tracking may be contained in bandwidth consumption 212.

In another embodiment, the device 202 may track its own data usage,shown as bandwidth consumption 210, and each of the other devices 206may track their own data usage, shown as bandwidth consumption 214. Insuch an embodiment, the bandwidth consumption 210 and the bandwidthconsumption 214 may be synchronized between the device 202 and devices206 such that the device 202 and the devices 206 retain an up-to-dateindication of the data usage for each of the devices individually andcollectively. In such an embodiment, the device 202 or the devices 206may periodically verify the collective data usage (e.g. for device 202and devices 206, etc.) with the bandwidth consumption 212 of server 204.In this manner, the device 202 and devices 206 may keep an accuraterecording of the collective bandwidth usage for all devices on anaccount.

In a separate embodiment, data usage may be tracked solely by device 202and devices 206. However, in such an embodiment, the collectivebandwidth consumption may not reflect the network carrier's data usage.For example, in one embodiment, a network carrier may not track usagefor a specific type of data transfer (e.g. use of Pandora music, etc.).In another embodiment, header data and/or other packet data may becounted in a different manner by the network carrier (and/or may noteven be detected by mobile device data usage counters, etc.). As such, aperiodic update to a server (e.g. network carrier database, etc.) mayassist in retaining accurate indications of bandwidth consumed.

In one embodiment, the need to determine bandwidth consumption may betriggered by a user initiating a sharing action which requires someamount of bandwidth consumption. For example, in one embodiment, a usermay upload a photo, stream a video, chat, and/or consume data in anymanner.

More illustrative information will now be set forth regarding variousoptional architectures and uses in which the foregoing method may or maynot be implemented, per the desires of the user. It should be stronglynoted that the following information is set forth for illustrativepurposes and should not be construed as limiting in any manner. Any ofthe following features may be optionally incorporated with or withoutthe exclusion of other features described.

FIG. 3A illustrates a digital photographic system 300, in accordancewith one embodiment. As an option, the digital photographic system 300may be implemented in the context of the details of any of the Figuresdisclosed herein. Of course, however, the digital photographic system300 may be implemented in any desired environment. Further, theaforementioned definitions may equally apply to the description below.

As shown, the digital photographic system 300 may include a processorcomplex 310 coupled to a camera module 330 via an interconnect 334. Inone embodiment, the processor complex 310 is coupled to a strobe unit336. The digital photographic system 300 may also include, withoutlimitation, a display unit 312, a set of input/output devices 314,non-volatile memory 316, volatile memory 318, a wireless unit 340, andsensor devices 342, each coupled to the processor complex 310. In oneembodiment, a power management subsystem 320 is configured to generateappropriate power supply voltages for each electrical load elementwithin the digital photographic system 300. A battery 322 may beconfigured to supply electrical energy to the power management subsystem320. The battery 322 may implement any technically feasible energystorage system, including primary or rechargeable battery technologies.Of course, in other embodiments, additional or fewer features, units,devices, sensors, or subsystems may be included in the system.

In one embodiment, a strobe unit 336 may be integrated into the digitalphotographic system 300 and configured to provide strobe illumination350 during an image sample event performed by the digital photographicsystem 300. In another embodiment, a strobe unit 336 may be implementedas an independent device from the digital photographic system 300 andconfigured to provide strobe illumination 350 during an image sampleevent performed by the digital photographic system 300. The strobe unit336 may comprise one or more LED devices, a gas-discharge illuminator(e.g. a Xenon strobe device, a Xenon flash lamp, etc.), or any othertechnically feasible illumination device. In certain embodiments, two ormore strobe units are configured to synchronously generate strobeillumination in conjunction with sampling an image. In one embodiment,the strobe unit 336 is controlled through a strobe control signal 338 toeither emit the strobe illumination 350 or not emit the strobeillumination 350. The strobe control signal 338 may be implemented usingany technically feasible signal transmission protocol. The strobecontrol signal 338 may indicate a strobe parameter (e.g. strobeintensity, strobe color, strobe time, etc.), for directing the strobeunit 336 to generate a specified intensity and/or color of the strobeillumination 350. The strobe control signal 338 may be generated by theprocessor complex 310, the camera module 330, or by any othertechnically feasible combination thereof. In one embodiment, the strobecontrol signal 338 is generated by a camera interface unit within theprocessor complex 310 and transmitted to both the strobe unit 336 andthe camera module 330 via the interconnect 334. In another embodiment,the strobe control signal 338 is generated by the camera module 330 andtransmitted to the strobe unit 336 via the interconnect 334.

Optical scene information 352, which may include at least a portion ofthe strobe illumination 350 reflected from objects in the photographicscene, is focused as an optical image onto an image sensor 332 withinthe camera module 330. The image sensor 332 generates an electronicrepresentation of the optical image. The electronic representationcomprises spatial color intensity information, which may includedifferent color intensity samples (e.g. red, green, and blue light,etc.). In other embodiments, the spatial color intensity information mayalso include samples for white light. The electronic representation istransmitted to the processor complex 310 via the interconnect 334, whichmay implement any technically feasible signal transmission protocol.

In one embodiment, input/output devices 314 may include, withoutlimitation, a capacitive touch input surface, a resistive tablet inputsurface, one or more buttons, one or more knobs, light-emitting devices,light detecting devices, sound emitting devices, sound detectingdevices, or any other technically feasible device for receiving userinput and converting the input to electrical signals, or convertingelectrical signals into a physical signal. In one embodiment, theinput/output devices 314 include a capacitive touch input surfacecoupled to a display unit 312. A touch entry display system may includethe display unit 312 and a capacitive touch input surface, also coupledto processor complex 310.

Additionally, in other embodiments, non-volatile (NV) memory 316 isconfigured to store data when power is interrupted. In one embodiment,the NV memory 316 comprises one or more flash memory devices (e.g. ROM,PCM, FeRAM, FRAM, PRAM, MRAM, NRAM, etc.). The NV memory 316 comprises anon-transitory computer-readable medium, which may be configured toinclude programming instructions for execution by one or more processingunits within the processor complex 310. The programming instructions mayimplement, without limitation, an operating system (OS), UI softwaremodules, image processing and storage software modules, one or moreinput/output devices 314 connected to the processor complex 310, one ormore software modules for sampling an image stack through camera module330, one or more software modules for presenting the image stack or oneor more synthetic images generated from the image stack through thedisplay unit 312. As an example, in one embodiment, the programminginstructions may also implement one or more software modules for mergingimages or portions of images within the image stack, aligning at leastportions of each image within the image stack, or a combination thereof.In another embodiment, the processor complex 310 may be configured toexecute the programming instructions, which may implement one or moresoftware modules operable to create a high dynamic range (HDR) image.

Still yet, in one embodiment, one or more memory devices comprising theNV memory 316 may be packaged as a module configured to be installed orremoved by a user. In one embodiment, volatile memory 318 comprisesdynamic random access memory (DRAM) configured to temporarily storeprogramming instructions, image data such as data associated with animage stack, and the like, accessed during the course of normaloperation of the digital photographic system 300. Of course, thevolatile memory may be used in any manner and in association with anyother input/output device 314 or sensor device 342 attached to theprocess complex 310.

In one embodiment, sensor devices 342 may include, without limitation,one or more of an accelerometer to detect motion and/or orientation, anelectronic gyroscope to detect motion and/or orientation, a magneticflux detector to detect orientation, a global positioning system (GPS)module to detect geographic position, or any combination thereof. Ofcourse, other sensors, including but not limited to a motion detectionsensor, a proximity sensor, an RGB light sensor, a gesture sensor, a 3-Dinput image sensor, a pressure sensor, and an indoor position sensor,may be integrated as sensor devices. In one embodiment, the sensordevices may be one example of input/output devices 314.

Wireless unit 340 may include one or more digital radios configured tosend and receive digital data. In particular, the wireless unit 340 mayimplement wireless standards (e.g. WiFi, Bluetooth, NFC, etc.), and mayimplement digital cellular telephony standards for data communication(e.g. CDMA, 3G, 4G, LTE, LTE-Advanced, etc.). Of course, any wirelessstandard or digital cellular telephony standards may be used.

In one embodiment, the digital photographic system 300 is configured totransmit one or more digital photographs to a network-based (online) or“cloud-based” photographic media service via the wireless unit 340. Theone or more digital photographs may reside within either the NV memory316 or the volatile memory 318, or any other memory device associatedwith the processor complex 310. In one embodiment, a user may possesscredentials to access an online photographic media service and totransmit one or more digital photographs for storage to, retrieval from,and presentation by the online photographic media service. Thecredentials may be stored or generated within the digital photographicsystem 300 prior to transmission of the digital photographs. The onlinephotographic media service may comprise a social networking service,photograph sharing service, or any other network-based service thatprovides storage of digital photographs, processing of digitalphotographs, transmission of digital photographs, sharing of digitalphotographs, or any combination thereof. In certain embodiments, one ormore digital photographs are generated by the online photographic mediaservice based on image data (e.g. image stack. HDR image stack, imagepackage, etc.) transmitted to servers associated with the onlinephotographic media service. In such embodiments, a user may upload oneor more source images from the digital photographic system 300 forprocessing by the online photographic media service.

In one embodiment, the digital photographic system 300 comprises atleast one instance of a camera module 330. In another embodiment, thedigital photographic system 300 comprises a plurality of camera modules330. Such an embodiment may also include at least one strobe unit 336configured to illuminate a photographic scene, sampled as multiple viewsby the plurality of camera modules 330. The plurality of camera modules330 may be configured to sample a wide angle view (e.g., greater thanforty-five degrees of sweep among cameras) to generate a panoramicphotograph. In one embodiment, a plurality of camera modules 330 may beconfigured to sample two or more narrow angle views (e.g., less thanforty-five degrees of sweep among cameras) to generate a stereoscopicphotograph. In other embodiments, a plurality of camera modules 330 maybe configured to generate a 3-D image or to otherwise display a depthperspective (e.g. a z-component, etc.) as shown on the display unit 312or any other display device.

In one embodiment, a display unit 312 may be configured to display atwo-dimensional array of pixels to form an image for display. Thedisplay unit 312 may comprise a liquid-crystal (LCD) display, alight-emitting diode (LED) display, an organic LED display, or any othertechnically feasible type of display. In certain embodiments, thedisplay unit 312 may be able to display a narrower dynamic range ofimage intensity values than a complete range of intensity values sampledfrom a photographic scene, such as within a single HDR image or over aset of two or more images comprising a multiple exposure or HDR imagestack. In one embodiment, images comprising an image stack may be mergedaccording to any technically feasible HDR blending technique to generatea synthetic image for display within dynamic range constraints of thedisplay unit 312. In one embodiment, the limited dynamic range mayspecify an eight-bit per color channel binary representation ofcorresponding color intensities. In other embodiments, the limiteddynamic range may specify more than eight-bits (e.g., 10 bits, 12 bits,or 14 bits, etc.) per color channel binary representation.

FIG. 3B illustrates a processor complex 310 within the digitalphotographic system 300 of FIG. 3A, in accordance with one embodiment.As an option, the processor complex 310 may be implemented in thecontext of the details of any of the Figures disclosed herein. Ofcourse, however, the processor complex 310 may be implemented in anydesired environment. Further, the aforementioned definitions may equallyapply to the description below.

As shown, the processor complex 310 includes a processor subsystem 360and may include a memory subsystem 362. In one embodiment, processorcomplex 310 may comprise a system on a chip (SoC) device that implementsprocessor subsystem 360, and memory subsystem 362 comprises one or moreDRAM devices coupled to the processor subsystem 360. In anotherembodiment, the processor complex 310 may comprise a multi-chip module(MCM) encapsulating the SoC device and the one or more DRAM devicescomprising the memory subsystem 362.

The processor subsystem 360 may include, without limitation, one or morecentral processing unit (CPU) cores 370, a memory interface 380,input/output interfaces unit 384, and a display interface unit 382, eachcoupled to an interconnect 374. The one or more CPU cores 370 may beconfigured to execute instructions residing within the memory subsystem362, volatile memory 318, NV memory 316, or any combination thereof.Each of the one or more CPU cores 370 may be configured to retrieve andstore data through interconnect 374 and the memory interface 380. In oneembodiment, each of the one or more CPU cores 370 may include a datacache, and an instruction cache. Additionally, two or more of the CPUcores 370 may share a data cache, an instruction cache, or anycombination thereof. In one embodiment, a cache hierarchy is implementedto provide each CPU core 370 with a private cache layer, and a sharedcache layer.

In some embodiments, processor subsystem 360 may include one or moregraphics processing unit (GPU) cores 372. Each GPU core 372 may comprisea plurality of multi-threaded execution units that may be programmed toimplement, without limitation, graphics acceleration functions. Invarious embodiments, the GPU cores 372 may be configured to executemultiple thread programs according to well-known standards (e.g.OpenGL™, WebGL™, OpenCL™, CUDA™, etc.), and/or any other programmablerendering graphic standard. In certain embodiments, at least one GPUcore 372 implements at least a portion of a motion estimation function,such as a well-known Harris detector or a well-known Hessian-Laplacedetector. Such a motion estimation function may be used at least in partto align images or portions of images within an image stack. Forexample, in one embodiment, an HDR image may be compiled based on animage stack, where two or more images are first aligned prior tocompiling the HDR image.

As shown, the interconnect 374 is configured to transmit data betweenand among the memory interface 380, the display interface unit 382, theinput/output interfaces unit 384, the CPU cores 370, and the GPU cores372. In various embodiments, the interconnect 374 may implement one ormore buses, one or more rings, a cross-bar, a mesh, or any othertechnically feasible data transmission structure or technique. Thememory interface 380 is configured to couple the memory subsystem 362 tothe interconnect 374. The memory interface 380 may also couple NV memory316, volatile memory 318, or any combination thereof to the interconnect374. The display interface unit 382 may be configured to couple adisplay unit 312 to the interconnect 374. The display interface unit 382may implement certain frame buffer functions (e.g. frame refresh, etc.).Alternatively, in another embodiment, the display unit 312 may implementcertain frame buffer functions (e.g. frame refresh, etc.). Theinput/output interfaces unit 384 may be configured to couple variousinput/output devices to the interconnect 374.

In certain embodiments, a camera module 330 is configured to storeexposure parameters for sampling each image associated with an imagestack. For example, in one embodiment, when directed to sample aphotographic scene, the camera module 330 may sample a set of imagescomprising the image stack according to stored exposure parameters. Asoftware module comprising programming instructions executing within aprocessor complex 310 may generate and store the exposure parametersprior to directing the camera module 330 to sample the image stack. Inother embodiments, the camera module 330 may be used to meter an imageor an image stack, and the software module comprising programminginstructions executing within a processor complex 310 may generate andstore metering parameters prior to directing the camera module 330 tocapture the image. Of course, the camera module 330 may be used in anymanner in combination with the processor complex 310.

In one embodiment, exposure parameters associated with images comprisingthe image stack may be stored within an exposure parameter datastructure that includes exposure parameters for one or more images. Inanother embodiment, a camera interface unit (not shown in FIG. 3B)within the processor complex 310 may be configured to read exposureparameters from the exposure parameter data structure and to transmitassociated exposure parameters to the camera module 330 in preparationof sampling a photographic scene. After the camera module 330 isconfigured according to the exposure parameters, the camera interfacemay direct the camera module 330 to sample the photographic scene; thecamera module 330 may then generate a corresponding image stack. Theexposure parameter data structure may be stored within the camerainterface unit, a memory circuit within the processor complex 310,volatile memory 318, NV memory 316, the camera module 330, or within anyother technically feasible memory circuit. Further, in anotherembodiment, a software module executing within processor complex 310 maygenerate and store the exposure parameter data structure.

FIG. 3C illustrates a digital camera 302, in accordance with oneembodiment. As an option, the digital camera 302 may be implemented inthe context of the details of any of the Figures disclosed herein. Ofcourse, however, the digital camera 302 may be implemented in anydesired environment. Further, the aforementioned definitions may equallyapply to the description below.

In one embodiment, the digital camera 302 may be configured to include adigital photographic system, such as digital photographic system 300 ofFIG. 3A. As shown, the digital camera 302 includes a camera module 330,which may include optical elements configured to focus optical sceneinformation representing a photographic scene onto an image sensor,which may be configured to convert the optical scene information to anelectronic representation of the photographic scene.

Additionally, the digital camera 302 may include a strobe unit 336, andmay include a shutter release button 315 for triggering a photographicsample event, whereby digital camera 302 samples one or more imagescomprising the electronic representation. In other embodiments, anyother technically feasible shutter release mechanism may trigger thephotographic sample event (e.g. such as a timer trigger or remotecontrol trigger, etc.).

FIG. 3D illustrates a wireless mobile device 376, in accordance with oneembodiment. As an option, the mobile device 376 may be implemented inthe context of the details of any of the Figures disclosed herein. Ofcourse, however, the mobile device 376 may be implemented in any desiredenvironment. Further, the aforementioned definitions may equally applyto the description below.

In one embodiment, the mobile device 376 may be configured to include adigital photographic system (e.g. such as digital photographic system300 of FIG. 3A), which is configured to sample a photographic scene. Invarious embodiments, a camera module 330 may include optical elementsconfigured to focus optical scene information representing thephotographic scene onto an image sensor, which may be configured toconvert the optical scene information to an electronic representation ofthe photographic scene. Further, a shutter release command may begenerated through any technically feasible mechanism, such as a virtualbutton, which may be activated by a touch gesture on a touch entrydisplay system comprising display unit 312, or a physical button, whichmay be located on any face or surface of the mobile device 376. Ofcourse, in other embodiments, any number of other buttons, externalinputs/outputs, or digital inputs/outputs may be included on the mobiledevice 376, and which may be used in conjunction with the camera module330.

As shown, in one embodiment, a touch entry display system comprisingdisplay unit 312 is disposed on the opposite side of mobile device 376from camera module 330. In certain embodiments, the mobile device 376includes a user-facing camera module 331 and may include a user-facingstrobe unit (not shown). Of course, in other embodiments, the mobiledevice 376 may include any number of user-facing camera modules orrear-facing camera modules, as well as any number of user-facing strobeunits or rear-facing strobe units.

In some embodiments, the digital camera 302 and the mobile device 376may each generate and store a synthetic image based on an image stacksampled by camera module 330. The image stack may include one or moreimages sampled under ambient lighting conditions, one or more imagessampled under strobe illumination from strobe unit 336, or a combinationthereof.

FIG. 3E illustrates camera module 330, in accordance with oneembodiment. As an option, the camera module 330 may be implemented inthe context of the details of any of the Figures disclosed herein. Ofcourse, however, the camera module 330 may be implemented in any desiredenvironment. Further, the aforementioned definitions may equally applyto the description below.

In one embodiment, the camera module 330 may be configured to controlstrobe unit 336 through strobe control signal 338. As shown, a lens 390is configured to focus optical scene information 352 onto image sensor332 to be sampled. In one embodiment, image sensor 332 advantageouslycontrols detailed timing of the strobe unit 336 though the strobecontrol signal 338 to reduce inter-sample time between an image sampledwith the strobe unit 336 enabled, and an image sampled with the strobeunit 336 disabled. For example, the image sensor 332 may enable thestrobe unit 336 to emit strobe illumination 350 less than onemicrosecond (or any desired length) after image sensor 332 completes anexposure time associated with sampling an ambient image and prior tosampling a strobe image.

In other embodiments, the strobe illumination 350 may be configuredbased on a desired one or more target points. For example, in oneembodiment, the strobe illumination 350 may light up an object in theforeground, and depending on the length of exposure time, may also lightup an object in the background of the image. In one embodiment, once thestrobe unit 336 is enabled, the image sensor 332 may then immediatelybegin exposing a strobe image. The image sensor 332 may thus be able todirectly control sampling operations, including enabling and disablingthe strobe unit 336 associated with generating an image stack, which maycomprise at least one image sampled with the strobe unit 336 disabled,and at least one image sampled with the strobe unit 336 either enabledor disabled. In one embodiment, data comprising the image stack sampledby the image sensor 332 is transmitted via interconnect 334 to a camerainterface unit 386 within processor complex 310. In some embodiments,the camera module 330 may include an image sensor controller, which maybe configured to generate the strobe control signal 338 in conjunctionwith controlling operation of the image sensor 332.

FIG. 3F illustrates a camera module 330, in accordance with oneembodiment. As an option, the camera module 330 may be implemented inthe context of the details of any of the Figures disclosed herein. Ofcourse, however, the camera module 330 may be implemented in any desiredenvironment. Further, the aforementioned definitions may equally applyto the description below.

In one embodiment, the camera module 330 may be configured to sample animage based on state information for strobe unit 336. The stateinformation may include, without limitation, one or more strobeparameters (e.g. strobe intensity, strobe color, strobe time, etc.), fordirecting the strobe unit 336 to generate a specified intensity and/orcolor of the strobe illumination 350. In one embodiment, commands forconfiguring the state information associated with the strobe unit 336may be transmitted through a strobe control signal 338, which may bemonitored by the camera module 330 to detect when the strobe unit 336 isenabled. For example, in one embodiment, the camera module 330 maydetect when the strobe unit 336 is enabled or disabled within amicrosecond or less of the strobe unit 336 being enabled or disabled bythe strobe control signal 338. To sample an image requiring strobeillumination, a camera interface unit 386 may enable the strobe unit 336by sending an enable command through the strobe control signal 338. Inone embodiment, the camera interface unit 386 may be included as aninterface of input/output interfaces 384 in a processor subsystem 360 ofthe processor complex 310 of FIG. 3B The enable command may comprise asignal level transition, a data packet, a register write, or any othertechnically feasible transmission of a command. The camera module 330may sense that the strobe unit 336 is enabled and then cause imagesensor 332 to sample one or more images requiring strobe illuminationwhile the strobe unit 336 is enabled. In such an implementation, theimage sensor 332 may be configured to wait for an enable signal destinedfor the strobe unit 336 as a trigger signal to begin sampling a newexposure.

In one embodiment, camera interface unit 386 may transmit exposureparameters and commands to camera module 330 through interconnect 334.In certain embodiments, the camera interface unit 386 may be configuredto directly control strobe unit 336 by transmitting control commands tothe strobe unit 336 through strobe control signal 338. By directlycontrolling both the camera module 330 and the strobe unit 336, thecamera interface unit 386 may cause the camera module 330 and the strobeunit 336 to perform their respective operations in precise timesynchronization. In one embodiment, precise time synchronization may beless than five hundred microseconds of event timing error. Additionally,event timing error may be a difference in time from an intended eventoccurrence to the time of a corresponding actual event occurrence.

In another embodiment, camera interface unit 386 may be configured toaccumulate statistics while receiving image data from camera module 330.In particular, the camera interface unit 386 may accumulate exposurestatistics for a given image while receiving image data for the imagethrough interconnect 334. Exposure statistics may include, withoutlimitation, one or more of an intensity histogram, a count ofover-exposed pixels, a count of under-exposed pixels, anintensity-weighted sum of pixel intensity, or any combination thereof.The camera interface unit 386 may present the exposure statistics asmemory-mapped storage locations within a physical or virtual addressspace defined by a processor, such as one or more of CPU cores 370,within processor complex 310. In one embodiment, exposure statisticsreside in storage circuits that are mapped into a memory-mapped registerspace, which may be accessed through the interconnect 334. In otherembodiments, the exposure statistics are transmitted in conjunction withtransmitting pixel data for a captured image. For example, the exposurestatistics for a given image may be transmitted as in-line data,following transmission of pixel intensity data for the captured image.Exposure statistics may be calculated, stored, or cached within thecamera interface unit 386.

In one embodiment, camera interface unit 386 may accumulate colorstatistics for estimating scene white-balance. Any technically feasiblecolor statistics may be accumulated for estimating white balance, suchas a sum of intensities for different color channels comprising red,green, and blue color channels. The sum of color channel intensities maythen be used to perform a white-balance color correction on anassociated image, according to a white-balance model such as agray-world white-balance model. In other embodiments, curve-fittingstatistics are accumulated for a linear or a quadratic curve fit usedfor implementing white-balance correction on an image.

In one embodiment, camera interface unit 386 may accumulate spatialcolor statistics for performing color-matching between or among images,such as between or among an ambient image and one or more images sampledwith strobe illumination. As with the exposure statistics, the colorstatistics may be presented as memory-mapped storage locations withinprocessor complex 310. In one embodiment, the color statistics aremapped in a memory-mapped register space, which may be accessed throughinterconnect 334, within processor subsystem 360. In other embodiments,the color statistics may be transmitted in conjunction with transmittingpixel data for a captured image. For example, in one embodiment, thecolor statistics for a given image may be transmitted as in-line data,following transmission of pixel intensity data for the image. Colorstatistics may be calculated, stored, or cached within the camerainterface 386.

In one embodiment, camera module 330 may transmit strobe control signal338 to strobe unit 336, enabling the strobe unit 336 to generateillumination while the camera module 330 is sampling an image. Inanother embodiment, camera module 330 may sample an image illuminated bystrobe unit 336 upon receiving an indication signal from camerainterface unit 386 that the strobe unit 336 is enabled. In yet anotherembodiment, camera module 330 may sample an image illuminated by strobeunit 336 upon detecting strobe illumination within a photographic scenevia a rapid rise in scene illumination. In one embodiment, a rapid risein scene illumination may include at least a rate of increasingintensity consistent with that of enabling strobe unit 336. In still yetanother embodiment, camera module 330 may enable strobe unit 336 togenerate strobe illumination while sampling one image, and disable thestrobe unit 336 while sampling a different image.

FIG. 3G illustrates camera module 330, in accordance with oneembodiment. As an option, the camera module 330 may be implemented inthe context of the details of any of the Figures disclosed herein. Ofcourse, however, the camera module 330 may be implemented in any desiredenvironment. Further, the aforementioned definitions may equally applyto the description below.

In one embodiment, the camera module 330 may be in communication with anapplication processor 335. The camera module 330 is shown to includeimage sensor 332 in communication with a controller 333. Further, thecontroller 333 is shown to be in communication with the applicationprocessor 335.

In one embodiment, the application processor 335 may reside outside ofthe camera module 330. As shown, the lens 390 may be configured to focusoptical scene information onto image sensor 332 to be sampled. Theoptical scene information sampled by the image sensor 332 may then becommunicated from the image sensor 332 to the controller 333 for atleast one of subsequent processing and communication to the applicationprocessor 335. In another embodiment, the controller 333 may controlstorage of the optical scene information sampled by the image sensor332, or storage of processed optical scene information.

In another embodiment, the controller 333 may enable a strobe unit toemit strobe illumination for a short time duration (e.g. less than onemicrosecond, etc.) after image sensor 332 completes an exposure timeassociated with sampling an ambient image. Further, the controller 333may be configured to generate strobe control signal 338 in conjunctionwith controlling operation of the image sensor 332.

In one embodiment, the image sensor 332 may be a complementary metaloxide semiconductor (CMOS) sensor or a charge-coupled device (CCD)sensor. In another embodiment, the controller 333 and the image sensor332 may be packaged together as an integrated system or integratedcircuit. In yet another embodiment, the controller 333 and the imagesensor 332 may comprise discrete packages. In one embodiment, thecontroller 333 may provide circuitry for receiving optical sceneinformation from the image sensor 332, processing of the optical sceneinformation, timing of various functionalities, and signaling associatedwith the application processor 335. Further, in another embodiment, thecontroller 333 may provide circuitry for control of one or more ofexposure, shuttering, white balance, and gain adjustment. Processing ofthe optical scene information by the circuitry of the controller 333 mayinclude one or more of gain application, amplification, andanalog-to-digital conversion. After processing the optical sceneinformation, the controller 333 may transmit corresponding digital pixeldata, such as to the application processor 335.

In one embodiment, the application processor 335 may be implemented onprocessor complex 310 and at least one of volatile memory 318 and NVmemory 316, or any other memory device and/or system. The applicationprocessor 335 may be previously configured for processing of receivedoptical scene information or digital pixel data communicated from thecamera module 330 to the application processor 335.

FIG. 4 illustrates a network service system 400, in accordance with oneembodiment. As an option, the network service system 400 may beimplemented in the context of the details of any of the Figuresdisclosed herein. Of course, however, the network service system 400 maybe implemented in any desired environment. Further, the aforementioneddefinitions may equally apply to the description below.

In one embodiment, the network service system 400 may be configured toprovide network access to a device implementing a digital photographicsystem. As shown, network service system 400 includes a wireless mobiledevice 376, a wireless access point 472, a data network 474, data center480, and a data center 481. The wireless mobile device 376 maycommunicate with the wireless access point 472 via a digital radio link471 to send and receive digital data, including data associated withdigital images. The wireless mobile device 376 and the wireless accesspoint 472 may implement any technically feasible transmission techniquesfor transmitting digital data via digital a radio link 471 withoutdeparting the scope and spirit of the present invention. In certainembodiments, one or more of data centers 480, 481 may be implementedusing virtual constructs so that each system and subsystem within agiven data center 480, 481 may comprise virtual machines configured toperform specified data processing and network tasks. In otherimplementations, one or more of data centers 480, 481 may be physicallydistributed over a plurality of physical sites.

The wireless mobile device 376 may comprise a smart phone configured toinclude a digital camera, a digital camera configured to includewireless network connectivity, a reality augmentation device, a laptopconfigured to include a digital camera and wireless networkconnectivity, or any other technically feasible computing deviceconfigured to include a digital photographic system and wireless networkconnectivity.

In various embodiments, the wireless access point 472 may be configuredto communicate with wireless mobile device 376 via the digital radiolink 471 and to communicate with the data network 474 via anytechnically feasible transmission media, such as any electrical,optical, or radio transmission media. For example, in one embodiment,wireless access point 472 may communicate with data network 474 throughan optical fiber coupled to the wireless access point 472 and to arouter system or a switch system within the data network 474. A networklink 475, such as a wide area network (WAN) link, may be configured totransmit data between the data network 474 and the data center 480.

In one embodiment, the data network 474 may include routers, switches,long-haul transmission systems, provisioning systems, authorizationsystems, and any technically feasible combination of communications andoperations subsystems configured to convey data between networkendpoints, such as between the wireless access point 472 and the datacenter 480. In one implementation, a wireless the mobile device 376 maycomprise one of a plurality of wireless mobile devices configured tocommunicate with the data center 480 via one or more wireless accesspoints coupled to the data network 474.

Additionally, in various embodiments, the data center 480 may include,without limitation, a switch/router 482 and at least one data servicesystem 484. The switch/router 482 may be configured to forward datatraffic between and among a network link 475, and each data servicesystem 484. The switch/router 482 may implement any technically feasibletransmission techniques, such as Ethernet media layer transmission,layer 2 switching, layer 3 routing, and the like. The switch/router 482may comprise one or more individual systems configured to transmit databetween the data service systems 484 and the data network 474.

In one embodiment, the switch/router 482 may implement session-levelload balancing among a plurality of data service systems 484. Each dataservice system 484 may include at least one computation system 488 andmay also include one or more storage systems 486. Each computationsystem 488 may comprise one or more processing units, such as a centralprocessing unit, a graphics processing unit, or any combination thereof.A given data service system 484 may be implemented as a physical systemcomprising one or more physically distinct systems configured to operatetogether. Alternatively, a given data service system 484 may beimplemented as a virtual system comprising one or more virtual systemsexecuting on an arbitrary physical system. In certain scenarios, thedata network 474 may be configured to transmit data between the datacenter 480 and another data center 481, such as through a network link476.

In another embodiment, the network service system 400 may include anynetworked mobile devices configured to implement one or more embodimentsof the present invention. For example, in some embodiments, apeer-to-peer network, such as an ad-hoc wireless network, may beestablished between two different wireless mobile devices. In suchembodiments, digital image data may be transmitted between the twowireless mobile devices without having to send the digital image data toa data center 480.

FIG. 5 illustrates a method 500 for determining whether to perform anaction, in accordance with another embodiment. As an option, the method500 may be carried out in the context of the details of any of theFigures. Of course, however, the method 500 may be carried out in anydesired environment. Further, the aforementioned definitions may equallyapply to the description below.

As shown, an action is initiated. See operation 502. Next, usage isqueried. See operation 504. Further, it is determined whether athreshold is surpassed. See decision 506.

In one embodiment, the action may require some amount of bandwidthconsumption, thereby necessitating querying for the amount of usage. Invarious embodiments, the usage may be associated with one or moredevices (e.g. single account with single device, single account withmultiple devices, etc.).

In another embodiment, the threshold may be imposed by a networkcarrier. For example, in one embodiment, a mobile plan may include abandwidth amount of 3 GB per billing cycle (e.g. on a monthly basis,etc.). As such, before initiating the action, it is verified whether thetotal usage amount may exceed the total bandwidth amount as monitored bythe network carrier.

Additionally, in one embodiment, verifying whether a threshold has beensurpassed may include verifying whether the devices have thus farsurpassed the data limit, or are coming within a set threshold of thelimit. In another embodiment, verifying whether a threshold has beensurpassed may include verifying whether the total amount thus far incombination with the amount of data needed to perform the action wouldsurpass a data limit.

As shown, if the threshold is not surpassed, the action is performed.See operation 512. However, if the threshold is surpassed, results aredisplayed. See operation 508. For example, in various embodiments,results being displayed may include providing a screen indicating thatperforming the action would cause the data usage to come within a setthreshold (e.g. within 10%, etc.) of the data limit. In anotherembodiment, the results being displayed may include providing a screenindicating that the data amount has been surpassed and the action cannotbe performed. In certain embodiments, total consumption may be displayedto a user regardless of whether the threshold is surpassed to assist theuser in tracking total usage of the account. Various embodiments mayimplement varying degrees of coherence with respect to usage data storedlocally within each device associated with a data plan.

In a separate embodiment, an option may be presented to the user wherebythe user may indicate the speed for transferring the data. For example,in one embodiment, the user may not need the data shared as quickly.Therefore, the user may select to share the data on a slower speed (e.g.2G, 3G, etc.). In one embodiment, the ability to select a speed may bepresented if a user has exceeded, or is within a percentage ofexceeding, the data usage threshold. For example, the user may elect totransmit data over a “4G” wireless connection (which may provideunlimited data usage under a plan) rather than an LTE wirelessconnection (which may provide limited data per month).

As shown, it is determined whether to proceed. See decision 510. In oneembodiment, an option to select “yes” or “no” may be presented to theuser, along with information indicating how much data remains on theaccount, and how much of the remaining data will be consumed byperforming the action. In one embodiment, the user may select topurchase an additional amount of data.

In another embodiment, the action to be performed may be delayed. Forexample, in one embodiment, it may be determined that the user is withina set amount of time (e.g. 2 days, etc.) until the next billing cycle(and allocation of data, etc.), and may choose to defer the action untilthe next cycle begins. In this manner, actions to be performed may bequeued until a new data allocation becomes available. In a separateembodiment, data becoming available may include determining that thedevice is connected to a separate network (e.g. without a datarestriction, such as a WiFi connection, etc.), thereby allowing theaction to be performed without affecting the data threshold and/orusage.

FIG. 6 illustrates a message sequence 600 for determining bandwidthconsumption, in accordance with another embodiment. As an option, themessage sequence 600 may be carried out in the context of the details ofany of the Figures. Of course, however, message sequence 600 may becarried out in any desired environment. Further, the aforementioneddefinitions may equally apply to the description below.

As shown, message sequence 600 includes device(s) 602, a data network604, and a network carrier 606.

At step one, the device initiates a sharing action. Sharing action maybe analogous to operation 502 in FIG. 5, the description disclosedherein. At step two, the data usage is queried for the device(s). In oneembodiment, the data usage may be associated with two or more devices.

At step three, the network carrier provides actual bandwidth consumptionamount. In one embodiment, the actual bandwidth consumption amount mayinclude the total amount of bandwidth consumed associated with thedevices on the account. In another embodiment, the actual bandwidthconsumption amount may indicate the total adjusted consumption, whereinone or more data items are excluded (e.g. music streaming, etc.) fromthe complete bandwidth usage.

At step four, the device(s) conditionally allow sharing action based onactual bandwidth consumption amount. In one embodiment, theconditionally allow may be analogous to operation 110 in FIG. 1, thedescription disclosed herein.

FIG. 7 illustrates a method 700 for reducing data associated with anaction, in accordance with another embodiment. As an option, the method700 may be carried out in the context of the details of any of theFigures. Of course, however, method 700 may be carried out in anydesired environment. Further, the aforementioned definitions may equallyapply to the description below.

As shown, an action is initiated. See operation 702. Next, usage isqueried. See operation 704. Further, a total amount of usage isdetermined. See operation 706.

In one embodiment, the action may require some amount of bandwidthconsumption, thereby necessitating querying for the amount of usage. Invarious embodiments, the usage may be associated with one or moredevices (e.g. single account with single device, single account withmultiple devices, etc.).

In another embodiment, the threshold may be imposed by a networkcarrier. For example, in one embodiment, a mobile plan may include abandwidth amount of 3 GB per billing cycle (e.g. on a monthly basis,etc.). As such, before initiating the action, it is verified whether thetotal usage amount may exceed the total bandwidth amount as monitored bythe network carrier.

Additionally, in one embodiment, verifying whether a threshold has beensurpassed may include verifying whether the devices have thus farsurpassed the data limit, or are coming within a set threshold of thelimit. In another embodiment, verifying whether a threshold has beensurpassed may include verifying whether the total amount thus far (e.g.the first bandwidth consumption of FIG. 1) in combination with theamount of data needed to perform the action (e.g. the second bandwidthconsumption of FIG. 1) would surpass a data limit.

As shown, it is determined whether a threshold is surpassed. Seedecision 708. As shown, if the threshold is not surpassed, the action isperformed. See operation 712. However, if the threshold is surpassed,then data associated with the action is reduced. See operation 710. Inone embodiment, data may be reduced by decreasing resolution, size,quality, etc. In another embodiment, if data is reduced below athreshold quality (e.g. as indicated by user feedback, etc.), then theaction associated with the data may not be performed. In a separateembodiment, a slider may be associated with the data reduction such thatmoving the slider may balance quality and data. For example, in oneembodiment, sliding a slider to the right might increase quality butalso increase size associated with the data. Additionally, sliding theslider to the left might decrease quality and decrease size associatedwith the data. Thus, in this manner, a user may control the quality anddata size associated with the action.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

What is claimed is:
 1. A computer program product embodied on anon-transitory computer readable medium, comprising: code for receivinga first sharing action; code for receiving a first bandwidthconsumption; code for receiving a second bandwidth consumption; code fordetermining whether a combination of the first bandwidth consumption andthe second bandwidth consumption surpasses a predefined threshold; andcode for conditionally allowing the first sharing action based on thedetermination.
 2. The computer program product of claim 1, wherein thecomputer program product is operable such that the first bandwidthconsumption is received from a network carrier.
 3. The computer programproduct of claim 1, wherein the computer program product is operablesuch that the second bandwidth consumption is received from a networkcarrier.
 4. The computer program product of claim 1, wherein thecomputer program product is operable such that the first bandwidthconsumption is calculated from consumption information received from apeer-to-peer network.
 5. The computer program product of claim 2,wherein the network carrier provides the first bandwidth consumption inresponse to a query of usage associated with a first user.
 6. Thecomputer program product of claim 3, wherein the network carrierprovides the second bandwidth consumption in response to a query ofusage associated with the first sharing action.
 7. The computer programproduct of claim 1, wherein the computer program product is operablesuch that specific types of data are not included in the first bandwidthconsumption and second bandwidth consumption.
 8. The computer programproduct of claim 1, wherein the computer program product is operablesuch that the first bandwidth consumption reflects actual bandwidthconsumption as calculated by a network carrier.
 9. The computer programproduct of claim 4, wherein the peer-to-peer network monitors bandwidthconsumption associated with two or more devices.
 10. The computerprogram product of claim 1, wherein the computer program product isoperable such that if the predefined threshold is surpassed, the firstsharing action is denied.
 11. The computer program product of claim 1,wherein the computer program product is operable such that if thepredefined threshold is not surpassed, the first sharing action is fullyallowed.
 12. The computer program product of claim 1, wherein thecomputer program product is operable such that the conditionallyallowing depends on an effect of the first sharing action.
 13. Thecomputer program product of claim 12, wherein the computer programproduct is operable such that the effect includes a total amount ofbandwidth utilized as a result of the first sharing action.
 14. Thecomputer program product of claim 1, wherein the computer programproduct is operable such that the first bandwidth consumption comprisesan amount of bandwidth consumed against a data allocation associatedwith a wireless data service, and the second bandwidth consumptioncomprises an amount of data associated with performing the first sharingaction.
 15. The computer program product of claim 1, wherein thecomputer program product is operable such that the predefined thresholdis associated with a predefined limit associated with a first account.16. The computer program product of claim 15, wherein the computerprogram product is operable such that the predefined threshold isadjusted.
 17. The computer program product of claim 16, wherein thecomputer program product is operable such that the adjustment includespurchasing additional bandwidth associated with the first account. 18.The computer program product of claim 1, wherein the computer programproduct is operable such the first bandwidth consumption and secondbandwidth consumption are received from a peer-to-peer network, thepeer-to-peer network periodically receiving updates from a networkcarrier regarding the first bandwidth consumption and the secondbandwidth consumption.
 19. An apparatus, comprising: circuitry for:receiving a first sharing action; receiving a first bandwidthconsumption; receiving a second bandwidth consumption; determiningwhether a combination of the first bandwidth consumption and the secondbandwidth consumption surpasses a predefined threshold; andconditionally allowing the first sharing action based on thedetermination.
 20. A method, comprising: receiving a first sharingaction; receiving a first bandwidth consumption; receiving a secondbandwidth consumption; determining whether a combination of the firstbandwidth consumption and the second bandwidth consumption surpasses apredefined threshold; and conditionally allowing the first sharingaction based on the determination.